is the
subcarrier offset from subcarrier 0 in common resource block 
to the lowest subcarrier is obtained
from the higher-layer parameter offsetToPointA.Please refer to RP-222645 for detailed scope of the WI on NR support for dedicated spectrum less than 5MHz for FR1.
This agenda item will not be treated in RAN1#110bis-e. No contributions please.
Please refer to RP-222645 for detailed scope of the WI on NR support for dedicated spectrum less than 5MHz for FR1.
R1-2212852 Session notes for 9.16 (NR support for dedicated spectrum less than 5MHz for FR1) Ad-hoc Chair (CMCC)
Endorsed and contents incorporated below.
[111-R18-<5MHz] – Yuanchao (Lenovo)
To be used for sharing updates on online/offline schedule, details on what is to be discussed in online/offline sessions, tdoc number of the moderator summary for online session, etc
R1-2212398 Work Plan for NR support for dedicated spectrum less than 5MHz for FR1 Nokia, Nokia Shanghai Bell
R1-2210834 Enhancements for less than 5 MHz dedicated spectrum FUTUREWEI
R1-2210869 Discussion on dedicated spectrum less than 5 MHz for FR1 Huawei, HiSilicon
R1-2211036 Discussion on NR support for dedicated spectrum less than 5MHz vivo
R1-2211050 Discussion on dedicated spectrum less than 5MHz for FR1 ZTE
R1-2211132 PBCH design for dedicated spectrum less than 5MHz for FR1 TD Tech, Chengdu TD Tech
R1-2211353 Views on enhancements to operate NR on dedicated spectrum less than 5 MHz xiaomi
R1-2211391 Discussion on NR operation with less than 5MHz Bandwidth Intel Corporation
R1-2211547 Discussion on enhancements to operate NR on dedicated spectrum Spreadtrum Communications
R1-2211572 Enhancements to operate NR on dedicated spectrum less than 5 MHz Lenovo
R1-2211770 NR support of spectrum less than 5MHz for FR1 Ericsson
R1-2212012 Discussion on enhancements to operate NR on dedicated spectrum less than 5 MHz NTT DOCOMO, INC.
R1-2212076 Enhancements to operate NR on dedicated spectrum less than 5 MHz Samsung
R1-2212148 NR support for dedicated spectrum less than 5MHz in FR1 Qualcomm Incorporated
R1-2212247 On dedicated spectrum less than 5 MHz MediaTek Inc.
R1-2212307 Discussion on enhancements for dedicated spectrum less than 5 MHz LG Electronics
R1-2212397 NR support for below 5 MHz BW Nokia, Nokia Shanghai Bell
R1-2212755 Summary of discussion on enhancements to operate NR on dedicated spectrum less than 5MHz Moderator (Lenovo)
From Nov 15th session
Agreement
In an LS to RAN4, in addition to reuse 5 MHz channel bandwidth, RAN1 suppose only 3 MHz channel bandwidth is supported, and would like to get RAN4 responses on the maximum transmission bandwidth (the number of PRBs) for this channel BW.
Agreement
RAN1 would like to ask RAN4 if finer sync. raster for the 3MHz and/or 5MHz channel bandwidth is feasible, as well as any input from RAN1 for RAN4’s answer to this question.
Agreement
Before getting RAN4 responses, RAN1 assume maximum transmission bandwidth, 15RBs or 16RBs for 3 MHz channel BW for evaluation and analysis.
Note: include agreement into the LS
Agreement
Before getting RAN4 responses, RAN1 assume that the UE could know which RBs are used for SSB transmission after PSS/SSS is detected for evaluation and analysis.
Note: it does not mean indication signaling is needed.
Note: include this agreement into the LS.
R1-2212888 Summary#2 of discussion on enhancements to operate NR on dedicated spectrum less than 5MHz Moderator (Lenovo)
From Nov 17th session
Agreement
Including following 2 questions into the LS
Question 1: RAN1’s understanding is that in addition to reuse 5 MHz channel bandwidth, RAN1 suppose only 3 MHz channel bandwidth is supported, and would like to get RAN4 responses on the maximum transmission bandwidth (the number of PRBs) for this channel BW
Question 2: RAN1 have discussed aspects related to synch raster in the spectrum of interest. RAN1 would like to ask RAN4 if finer sync. raster for the 3MHz and/or 5MHz channel bandwidth is feasible, as well as if RAN4 needs any input from RAN1.
R1-2212898 [Draft] LS on NR support for dedicated spectrum less than 5MHz for FR1 Nokia
Decision: From Nov 17th session, the draft LS to RAN4 R1-2212898 is endorsed in principle with the modified questions as agreed above and all agreements and conclusions made in RAN1#111. Final LS is approved in R1-2212919.
For transmission bandwidths of <5MHz for 3MHz and 5MHz channel bandwidth, a subset of PRBs of 20-PRB PBCH are used for PBCH transmission if the transmission BW of a channel is less than 20PRBs.
· FFS which PRBs are used and how to use the PRBs
· Note: PRBs for PSS/SSS are not punctured.
Agreement
For CORESET#0 configuration for transmission bandwidths <5 MHz for 3MHz and 5MHz channel bandwidth, following options are for study,
· Opt.1: Existing configuration table for 15kHz SCS, 5MHz minimum channel BW (i.e., table 13-1 in TS38.213) is reused for configuration
· Opt.2: A new CORESET#0 configuration table is to be introduced for the configuration.
Conclusion
No enhancements are required for PRACH to operate NR on transmission bandwidths of <5MHz for 3MHz and 5MHz channel bandwidth.
· Note: PRACH formats and configurations not fitting into the transmission BW are not applicable
Agreement
Short PRACH formats with 15kHz SCS, and long PRACH formats with 1.25kHz SCS are supported for transmission bandwidths <5 MHz for 3MHz and 5MHz channel bandwidth.
Conclusion
No enhancements are needed for PUCCH to support transmission bandwidths of <5MHz for 3MHz and 5MHz channel bandwidth,
· FFS: the necessity for PUCCH FH disabling.
Agreement
Study whether and how to recover PDCCH detection performance of CORESET#0 for transmission bandwidths of <5MHz for 3MHz and 5MHz channel bandwidth. The following options are considered,
· Opt.1: Power boosting
· Opt.2: Non-interleaved CCE-to-REG mapping
· Opt.3: A new interleaver to ensure PDCCH is fully mapped in the spectrum
· Opt.4: New aggregation level(s) for fit in the spectrum
· Opt.5: PDCCH rate matching
· Opt.6.: no enhancement specified
Agreement
Study whether and how to recover PBCH detection performance for transmission bandwidths of <5MHz for 3MHz and 5MHz channel bandwidth. The following options are considered,
· Opt.1: Power boosting
· Opt.2: Multiple PBCH receptions
· Opt.3: PBCH remapping
· Opt.4: PBCH payload reduction
· Opt.5: PBCH rate matching around the punctured PRBs
· Opt.6: no enhancement specified
Please refer to RP-222645 for detailed scope of the WI on NR support for dedicated spectrum less than 5MHz for FR1.
R1-2302071 Session notes for 9.16 (NR support for dedicated spectrum less than 5MHz for FR1) Ad-hoc Chair (CMCC)
[112-R18-FR1<5MHz] – Yuantao (Lenovo)
To be used for sharing updates on online/offline schedule, details on what is to be discussed in online/offline sessions, tdoc number of the moderator summary for online session, etc
R1-2300059 Discussion on enhancements for less than 5 MHz dedicated spectrum FUTUREWEI
R1-2300115 Discussion on dedicated spectrum less than 5 MHz for FR1 Huawei, HiSilicon
R1-2300247 Discussion on enhancements to operate NR on dedicated spectrum Spreadtrum Communications
R1-2300316 Open issues of dedicated spectrum less than 5MHz for FR1 TD Tech, Chengdu TD Tech
R1-2300347 Discussion on dedicated spectrum less than 5MHz for FR1 ZTE
R1-2300483 Discussion on NR support for dedicated spectrum less than 5MHz vivo
R1-2300565 Views on enhancements to operate NR on dedicated spectrum less than 5 MHz xiaomi
R1-2300786 Discussion on enhancements to operate NR on dedicated spectrum less than 5 MHz NICT
R1-2300859 Enhancements to operate NR on dedicated spectrum less than 5 MHz Lenovo
R1-2300975 Discussion on NR operation with less than 5MHz Bandwidth Intel Corporation
R1-2301096 NR support for below 5 MHz BW Nokia, Nokia Shanghai Bell
R1-2301114 Discussion on enhancements for dedicated spectrum less than 5 MHz LG Electronics
R1-2301154 NR support of spectrum less than 5MHz for FR1 Ericsson
R1-2301296 Enhancements to operate NR on dedicated spectrum less than 5 MHz Samsung
R1-2301378 On dedicated spectrum less than 5MHz for FR1 Apple
R1-2301445 NR support for dedicated spectrum less than 5MHz in FR1 Qualcomm Incorporated
R1-2301463 On enhancements to operate NR on dedicated spectrum less than 5 MHz KT Corp.
R1-2301523 Discussion on enhancements to operate NR on dedicated spectrum less than 5 MHz NTT DOCOMO, INC.
R1-2301784 On dedicated spectrum less than 5 MHz MediaTek Inc. (rev of R1-2301610)
R1-2301975 Summary of discussion on enhancements to operate NR on dedicated spectrum less than 5MHz Moderator (Lenovo)
From Monday session
Conclusion
For transmission bandwidths of <5MHz for 3MHz channel bandwidth, for CSI-RS other than for RRM measurements, no enhancements are needed.
· FFS: CSI-RS for RRM
R1-2302132 Summary of discussion on enhancements to operate NR on dedicated spectrum less than 5MHz Moderator (Lenovo)
From Thursday session
Agreement
Working Assumption
For transmission bandwidth[s] of <5MHz, for PBCH, in the case[s] that available PRBs for PBCH transmission are less than 20PRB,
· PBCH based on RB-level puncturing (i.e., PBCH encoding is based on 20PRB. The encoded bits and DMRS are mapped to 20PRBs based on legacy SSB structure, and those PRBs that fall outside of available PRBs for PBCH transmission are punctured)
· Note: No other optimization is needed
R1-2302157 DRAFT LS to RAN on transmission bandwidths for NR on dedicated spectrum less than 5 MHz Moderator (Nokia)
Decision: Draft LS in R1-2302157 is endorsed in principle. Final LS is approved in R1-2302186.
Final summary in R1-2302219.
No contributions in RAN1#112bis-e.
Please refer to RP-230186 for detailed scope of the WI on NR support for dedicated spectrum less than 5MHz for FR1. Rapporteur to provide initial input on higher layer signalling under agenda item 9.13. For input on higher layer signalling from any other source, please include it as part of your tdoc to relevant sub-agenda items.
R1-2306149 Session notes for 9.13 (NR support for dedicated spectrum less than 5MHz for FR1) Ad-Hoc Chair (CMCC)
[113-R18-FR1<5MHz] – Yuantao (Lenovo)
Email discussion on NR support for dedicated spectrum less than 5MHz
- To be used for sharing updates on online/offline schedule, details on what is to be discussed in online/offline sessions, tdoc number of the moderator summary for online session, etc
R1-2304360 Discussion on less than 5 MHz dedicated spectrum FUTUREWEI
R1-2304506 Discussion on NR support for dedicated spectrum less than 5MHz vivo
R1-2304583 Discussion on enhancements to operate NR on dedicated spectrum Spreadtrum Communications
R1-2304601 Discussion on Enhancements to operate NR on dedicated spectrum less than 5 MHz ZTE
R1-2304630 Discussion on dedicated spectrum less than 5 MHz for FR1 Huawei, HiSilicon
R1-2304887 Discussion on enhancements to operate NR on dedicated spectrum less than 5 MHz xiaomi
R1-2304978 Enhancements to operate NR on dedicated spectrum less than 5 MHz Lenovo
R1-2305026 NR support for below 5 MHz BW Nokia, Nokia Shanghai Bell
R1-2305148 Discussion on enhancements for dedicated spectrum less than 5 MHz LG Electronics
R1-2305185 NR support of spectrum less than 5MHz for FR1 Ericsson
R1-2305274 NR support of spectrum less than 5MHz for FR1 Apple
R1-2305364 NR support for dedicated spectrum less than 5MHz for FR1 Qualcomm Incorporated
R1-2305541 Enhancements to operate NR on dedicated spectrum less than 5 MHz Samsung
R1-2305550 Discussion on operation of NR on dedicated spectrum less than 5 MHz Rakuten Mobile, Inc
R1-2305619 Discussion on enhancements to operate NR on dedicated spectrum less than 5 MHz NTT DOCOMO, INC.
R1-2305629 Open issues of dedicated spectrum less than 5MHz for FR1 TD Tech, Chengdu TD Tech
R1-2305984 On dedicated spectrum less than 5 MHz MediaTek Inc. (rev of R1-2305648)
R1-2306107 Summary#1 of discussion on enhancements to operate NR on dedicated spectrum less than 5MHz Moderator (Lenovo)
From Tuesday session
Agreement
If working assumption made in RAN1#112 is confirmed,
For 12PRBs PBCH transmission BW for 3MHz channel BW, the upper 4PRBs and lower 4PRBs of NR 20PRBs PBCH are punctured, otherwise,
For 12PRBs PBCH transmission BW for 3MHz channel BW, the upper 4PRBs and lower 4PRBs of NR 20PRBs PBCH are not used.
R1-2306154 Summary#2 of discussion on enhancements to operate NR on dedicated spectrum less than 5MHz Moderator (Lenovo)
Presented in Wednesday session
R1-2306218 Summary#3 of discussion on enhancements to operate NR on dedicated spectrum less than 5MHz Moderator (Lenovo)
From Thursday session
Agreement
Agreement
Confirm following RAN1#112 working assumption
Working Assumption
For transmission bandwidth[s] of <5MHz, for PBCH, in the case[s] that available PRBs for PBCH transmission is less than 20PRB,
· PBCH based on RB-level puncturing (i.e., PBCH encoding is based on 20PRB. The encoded bits and DMRS are mapped to 20PRBs based on legacy SSB structure, and those PRBs that fall outside of available PRBs for PBCH transmission are punctured)
· Note: No other optimization is needed
From AI 5 of RAN1#112bis-e
R1-2302269 Reply LS on NR support for dedicated spectrum less than 5 MHz for FR1 RAN4, Qualcomm
R1-2306240 DRAFT Reply LS on NR support for dedicated spectrum less than 5 MHz for FR1 Moderator (Nokia)
Decision: The draft LS is endorsed in principle. Final LS is approved in R1-2306241.
Please refer to RP-231425 for detailed scope of the WI on NR support for dedicated spectrum less than 5MHz for FR1. Including any input on higher layer signaling (provide input as part of tdoc in each sub-agenda item).
R1-2308552 Session notes for 9.13 (NR support for dedicated spectrum less than 5MHz for FR1) Ad-Hoc Chair (CMCC)
Endorsed and contents incorporated below.
[114-R18-FR1<5MHz] – Yuantao (Lenovo)
Email discussion on NR support for dedicated spectrum less than 5MHz
- To be used for sharing updates on online/offline schedule, details on what is to be discussed in online/offline sessions, tdoc number of the moderator summary for online session, etc
R1-2306393 Open issues of dedicated spectrum less than 5MHz for FR1 TD Tech, Chengdu TD Tech
R1-2306437 Discussion on less than 5 MHz dedicated spectrum FUTUREWEI
R1-2306531 Discussion on dedicated spectrum less than 5 MHz for FR1 Huawei, HiSilicon
R1-2306670 Discussion on enhancements to operate NR on dedicated spectrum Spreadtrum Communications
R1-2306775 Remaining issues on NR support for dedicated spectrum less than 5MHz vivo
R1-2306897 NR support for below 5 MHz BW Nokia, Nokia Shanghai Bell
R1-2306987 Discussion on NR operation for dedicated spectrum less than 5 MHz ZTE
R1-2307308 NR support of spectrum less than 5MHz for FR1 Apple
R1-2307361 Discussion on enhancements to operate NR on dedicated spectrum less than 5 MHz xiaomi
R1-2307415 Enhancements to operate NR on dedicated spectrum less than 5 MHz Lenovo
R1-2307495 Discussion on enhancements to operate NR on dedicated spectrum less than 5 MHz NTT DOCOMO, INC.
R1-2307705 Enhancements to operate NR on dedicated spectrum less than 5 MHz Samsung
R1-2307770 Discussion on Enhancements on NR dedicated spectrum less than 5MH Transsion Holdings
R1-2307796 Discussion on enhancements for dedicated spectrum less than 5 MHz LG Electronics
R1-2307800 NR support of spectrum less than 5MHz for FR1 Ericsson
R1-2307954 NR support for dedicated spectrum less than 5MHz for FR1 Qualcomm Incorporated
R1-2308040 On dedicated spectrum less than 5 MHz MediaTek Inc.
R1-2308406 Summary#1 of discussion on enhancements to operate NR on dedicated spectrum less than 5MHz Moderator (Lenovo)
From Tuesday session
Agreement
For 3MHz channel BW, the 15 PRBs CORESET#0 is obtained by puncturing the 9 upper PRBs of 𝑁RB CORESET = 24 CORESET#0.
Agreement (revised in Friday session)
For 3MHz channel BW, for kssb and PRB offset for the determining the CORESET#0 position in frequency domain,
Note: the above assumes that PRB offset to be the frequency gap between the first PRB of the actually transmitted 12/15 PRBs CORESET#0 and the first CRB overlapping with the first PRB of the actually transmitted 12 PRBs SS/PBCH block, how to capture it in the specification is left to editors.
R1-2308422 Summary#2 of discussion on enhancements to operate NR on dedicated spectrum less than 5MHz Moderator (Lenovo)
From Wednesday session
Agreement
For CORESET#0 for less than 5MHz transmission bandwidth, the UE assumes the same precoding being used per REG bundle.
Note: This depends on UE implementation whether channel estimation can be performed for partial REG bundle, if any.
R1-2308587 Summary#3 of discussion on enhancements to operate NR on dedicated spectrum less than 5MHz Moderator (Lenovo)
From Friday session
Agreement
Revise the previous agreement as below,
Agreement
For 3MHz channel BW, for kssb and PRB offset for the determining the CORESET#0 position in frequency domain,
· kssb follows legacy configuration.
o Note: based on existing specifications, UE
does not expect other values than kssb = 0 for 12PRBs CORESET#0,
[kssb
= 8 [or 20] for 15PRBs CORESET#0 with offset 0 PRBs, kssb = 4 [or 16] for
15RPBs CORESET#0 with offset 2 PRBs]
· PRB offset
o For 12 PRBs CORESET#0 transmission BW, PRB offset = 0
o For 15 PRBs CORESET#0 transmission BW, at
least PRB offset = 0, [2] 2 are
supported
§ FFS if offset = 1, 3 are supported.
Note: the above assumes that PRB offset to be the frequency gap between the first PRB of the actually transmitted 12/15 PRBs CORESET#0 and the first CRB overlapping with the first PRB of the actually transmitted 12 PRBs SS/PBCH block, how to capture it in the specification is left to editors.
Note: the range of the PRB offsets is only applicable to the introduced new sync. raster points for 3MHz channel BW and 100kHz channel raster.
Agreement
For 3MHz channel BW, Table 13-0 is used by the UE for CORESET#0 configuration only when the detected SSB is from a new synch raster point in RAN4.
FFS: any specification impact.
Agreement
For dedicated spectrum with less than 5MHz transmission BW, if a UE is not provided initialDownlinkBWP, the location and size of the initial DL BWP is equal to that of CORESET#0 transmission BW, i.e.,
Note: whether/how to reflect the above is up to Editor.
Conclusion (based on RAN1#113 agreement)
For 2 symbols and 3 symbols for 15 PRBs CORESET#0, both interleaved and non-interleaved CCE to REG mapping are supported.
Agreement
For 5MHz channel BW, 20 PRBs CORESET#0 transmission BW is supported.
Final summary in R1-2308607.
R1-2310548 Session notes for 8.9 (Maintenance on NR support for dedicated spectrum less than 5MHz for FR1) Ad-Hoc Chair (CMCC)
Friday decision: The session notes are endorsed and contents reflected below.
[114bis-R18-FR1<5MHz] – Yuantao (Lenovo)
Email discussion on NR support for dedicated spectrum less than 5MHz
- To be used for sharing updates on online/offline schedule, details on what is to be discussed in online/offline sessions, tdoc number of the moderator summary for online session, etc
R1-2309902 Introduction of NR support for dedicated spectrum less than 5MHz for FR1 to TS 38.300 Nokia (Rapporteur)
Discussion postponed to next meeting.
R1-2308897 Maintenance of dedicated spectrum less than 5 MHz Huawei, HiSilicon
R1-2308941 Discussion on less than 5 MHz dedicated spectrum FUTUREWEI
R1-2308997 Maintenance on enhancements to operate NR on dedicated spectrum Spreadtrum Communications
R1-2309134 Remaining issues on dedicated spectrum less than 5 MHz ZTE
R1-2309248 NR support for below 5 MHz BW Nokia, Nokia Shanghai Bell
R1-2309305 Remaining issues of enhancements for dedicated spectrum less than 5 MHz LG Electronics
R1-2309388 Remaining issues for enhancements to operate NR on dedicated spectrum less than 5 MHz Samsung
R1-2309653 Open issues of dedicated spectrum less than 5MHz for FR1 TD Tech, Chengdu TD Tech
R1-2309805 Remaining issues on dedicated spectrum less than 5 MHz Lenovo
R1-2309845 NR support of spectrum less than 5MHz for FR1 Apple
R1-2309889 Maintenance on NR support of spectrum less than 5MHz for FR1 Ericsson
R1-2309975 Maintenance on dedicated spectrum less than 5MHz MediaTek Inc.
R1-2310044 Remaining issues on enhancements to operate NR on dedicated spectrum less than 5 MHz NTT DOCOMO, INC.
R1-2310154 NR support for dedicated spectrum less than 5MHz for FR1 Qualcomm Incorporated
R1-2310377 Summary#1 of discussion on enhancements to operate NR on dedicated spectrum less than 5MHz Moderator (Lenovo)
Presented in Monday session.
R1-2310378 Summary#2 of discussion on enhancements to operate NR on dedicated spectrum less than 5MHz Moderator (Lenovo)
From Wednesday session
Working Assumption
For 3MHz channel BW,
· For the new sync. raster point (=920.73MHz, GSCN 41637 on band n100), UE supports 12 PRB BWP
· For other new sync raster points, UE supports 15 PRB BWP
o Note: it does not introduce any new interpretation on FG6-1
Note: it will be a conclusion when this working assumption is confirmed.
R1-2310498 Summary#3 of discussion on enhancements to operate NR on dedicated spectrum less than 5MHz Moderator (Lenovo)
From Thursday session
Conclusion
No consensus in RAN1 to support any enhancements for CSI-RS/TRS for dedicated spectrum less than 5MHz transmission BW.
Note: it is RAN1 understanding that the UE is not expected to use CSI-RS for RRM measurements for dedicated spectrum less than 5MHz transmission BW.
Conclusion
No consensus in RAN1 to support any enhancements for common PUCCH for dedicated spectrum less than 5MHz transmission BW.
Agreement
· Adopt following text proposals to Section7.4.3.1, TS38.211 in principle,
---------------------------------------------<Omitted text>--------------------------------------
The
quantity is the
subcarrier offset from subcarrier 0 in common resource block to the lowest subcarrier 0 of the SS/PBCH block after puncturing, if any, where is obtained
from the higher-layer parameter offsetToPointA.
---------
For an SS/PBCH block, the UE shall assume
-
antenna port 
is used for
transmission of PSS, SSS, PBCH and DM-RS for PBCH,
- ……………
-
the centre of subcarrier 0 of resource block coincides
with the centre of subcarrier 0 of a common resource block with the subcarrier
spacing
o provided by the higher-layer parameter subCarrierSpacingCommon for operation without shared spectrum channel access in FR1 and FR2-1; and
o same as the subcarrier spacing of the SS/PBCH block for operation without shared spectrum access in FR2-2 and for operation with shared spectrum channel access.
-
This common resource block overlaps with
subcarrier 0 of the first lowest resource block of
the SS/PBCH block after
puncturing, if any.
---------------------------------------------<Omitted text>--------------------------------------
Agreement
· Adopt following text proposal to section 4.4.4.2, TS38.211 in principle.
---------------------------------------------<Omitted text>--------------------------------------
offsetToPointA for a PCell downlink where offsetToPointA represents the frequency offset between point A and the lowest subcarrier of the lowest resource block, which overlaps with the SS/PBCH block after puncturing, if any, used by the UE for initial cell selection, expressed in units of resource blocks assuming 15 kHz subcarrier spacing for FR1 and 60 kHz subcarrier spacing for FR2…
---------------------------------------------<Omitted text>--------------------------------------
Agreement
· For non-interleaved CCE to REG mapping for 3MHz channel BW for 15 PRB CORESET#0, f(x) = x.
· For interleaved CCE to REG mapping for dedicated spectrum with transmission BW less than 5MHz, nshift = cell ID as in legacy.
Conclusion
· For 3MHz channel BW for the sync. raster point (920.73MHz, GSCN 41637), the UE shall support 12 PRB CORESET#0 during initial access.
· For 3MHz channel BW for the sync. raster points for 15 PRB transmission BW, the UE shall support 15 PRB CORESET#0 during initial access.
For 38.211 editor:
The above endorsed text proposals for TS 38.211 are also collected in R1-2310569. Please consider them in the next specification revision.
R1-2310569 Summary on the agreed text proposals for dedicated spectrum less than 5MHz Moderator (Lenovo)
R1-2312508 Session notes for 8.9 (Maintenance on NR support for dedicated spectrum less than 5MHz for FR1) Ad-Hoc Chair (Huawei)
Friday decision: The session notes are endorsed and contents reflected below.
[115-R18-FR1<5MHz] – Yuantao (Lenovo)
Email discussion on NR support for dedicated spectrum less than 5MHz
- To be used for sharing updates on online/offline schedule, details on what is to be discussed in online/offline sessions, tdoc number of the moderator summary for online session, etc
R1-2311357 Introduction of NR support for dedicated spectrum less than 5MHz for FR1 to TS 38.300 Nokia (WI Rapporteur)
From Tuesday session
Agreement
Endorse the TP below for TS 38.300 and send it in an LS to RAN2
|
Reason for change: |
Introduction of changes related to WI “NR support for dedicated spectrum less than 5MHz for FR1” |
|
|
|
|
Summary of change: |
Adding a remark that with 3MHz Channel BW the PBCH is punctured down to 144 subcarriers (i.e. 12 PRBs) |
|
|
|
|
Consequences if not approved: |
Incomplete description of the PBCH in case of operation with 3MHz CBW. |
--- < Start of the Text Proposal > ---
<Unchanged text omitted>
5.2.4 Synchronization signal and PBCH block
The Synchronization Signal and PBCH block (SSB) consists of primary and secondary synchronization signals (PSS, SSS), each occupying 1 symbol and 127 subcarriers, and PBCH spanning across 3 OFDM symbols and 240 subcarriers, but on one symbol leaving an unused part in the middle for SSS as show in Figure 5.2.4-1. For the 3 MHz channel bandwidth, the PBCH is further equally punctured from both edges to span 144 subcarriers. The possible time locations of SSBs within a half-frame are determined by sub-carrier spacing and the periodicity of the half-frames where SSBs are transmitted is configured by the network. During a half-frame, different SSBs may be transmitted in different spatial directions (i.e. using different beams, spanning the coverage area of a cell).
Within the frequency span of a carrier, multiple SSBs can be transmitted. The PCIs of SSBs transmitted in different frequency locations do not have to be unique, i.e. different SSBs in the frequency domain can have different PCIs. However, when an SSB is associated with an RMSI, the SSB is referred to as a Cell-Defining SSB (CD-SSB). A PCell is always associated to a CD-SSB located on the synchronization raster.
Figure 5.2.4-1: Time-frequency structure of SSB
Polar coding is used for PBCH.
The UE may assume a band-specific sub-carrier spacing for the SSB unless a network has configured the UE to assume a different sub-carrier spacing.
PBCH symbols carry its own frequency-multiplexed DMRS.
QPSK modulation is used for PBCH.
The PBCH physical layer model is described in TS 38.202 [20].
<Unchanged text omitted>
--- < End of the Text Proposal > ---
Comeback for draft LS
R1-2312457 DRAFT LS on Introduction of NR support for dedicated spectrum less than 5MHz for FR1 to TS 38.300 Moderator (Nokia)
Thursday decision: The draft LS in R1-2312457 is endorsed. Final LS is approved in R1-2312458.
R1-2310966 Maintenance on NR support of spectrum less than 5MHz for FR1 Ericsson
R1-2311022 Remaining issues on dedicated spectrum less than 5 MHz ZTE
R1-2311355 Discussion on enhancements to operate NR on dedicated spectrum less than 5MHz CATT
R1-2311356 NR support for below 5 MHz BW Nokia, Nokia Shanghai Bell
R1-2311633 Remaining issues on enhancements to operate NR on dedicated spectrum less than 5 MHz NTT DOCOMO, INC.
R1-2311725 Remaining issues on dedicated spectrum less than 5 MHz Lenovo
R1-2311857 Maintenance on enhancements to operate NR on dedicated spectrum less than 5 MHz Samsung
R1-2311898 Remaining issues of enhancements for dedicated spectrum less than 5 MHz LG Electronics
R1-2311988 Maintenance on dedicated spectrum less than 5MHz MediaTek Inc.
R1-2312048 NR support for dedicated spectrum less than 5MHz for FR1 Qualcomm Incorporated
R1-2312133 Further discussion on dedicated spectrum less than 5MHz for FR1 TD Tech, Chengdu TD Tech
R1-2312151 Enhancements to operate NR on dedicated spectrum less than 5 MHz Huawei, HiSilicon
R1-2312397 Summary#1 of discussion on enhancements to operate NR on dedicated spectrum less than 5MHz Moderator (Lenovo)
From Tuesday session
Agreement
Confirm the following working assumption as a conclusion.
|
Working Assumption For 3MHz channel BW, - For the new sync. raster point (=920.73MHz, GSCN 41637 on band n100), UE supports 12 PRB BWP - For other new sync raster points, UE supports 15 PRB BWP o Note: it does not introduce any new interpretation on FG6-1 Note: it will be a conclusion when this working assumption is confirmed |
R1-2312398 Summary#2 of discussion on enhancements to operate NR on dedicated spectrum less than 5MHz Moderator (Lenovo)
R1-2312567 Summary#3 of discussion on enhancements to operate NR on dedicated spectrum less than 5MHz Moderator (Lenovo)
From Thursday session
Agreement
The TP in Proposal 6-1 in section 6 of R1-2312567 for TS38.213 clause 10.1 is endorsed.
Conclusion
For the 
and 
for PUCCH resource determination for CORESET#0, the CORESET for
PUCCH resource determination is obtained as described in clause 7.3.2.2 of [4,
TS 38.211] before puncturing if applicable.
Agreement
The TP in Proposal 6-3 in section 6 of R1-2312567 for TS38.214 clause 5.1 in endorsed.
R1-2312563 DRAFT LS on inter-frequency neighbour cells supporting NR dedicated spectrum less than 5 MHz for FR1 Qualcomm Incorporated
Proposal 6-4
RAN1 to send an LS to RAN2 (cc RAN4) on any backward compatibility issue of inter-frequency neighbour cell list for single carrier operation in NR dedicated spectrum less than 5 MHz for FR1.
R1-2312602 DRAFT LS on inter-frequency neighbour cells supporting NR dedicated spectrum less than 5 MHz for FR1 Qualcomm Incorporated
Friday decision: The draft LS to RAN2 and RAN4 in R1-2312602 is endorsed. Final LS is approved in R1-2312668.